Reduced data access time on tape with data redundancy

ABSTRACT

A computer-implemented method, according to one embodiment, includes: selecting a first tape to write a first copy of a first portion of data to, sending an instruction to write the first copy of the first portion of data to a first partition on the first tape, wherein the first tape has at least the first partition and a second partition, selecting a second tape that is different than the first tape to write a second copy of the first portion of data to, and sending an instruction to write the second copy of the first portion of data to a second partition on the second tape, wherein the second tape has at least a first partition and the second partition. The first partition on each of the first and second tapes is closer to a beginning of the respective tape than the second partition on the respective tape.

BACKGROUND

The present invention relates to data storage systems, and moreparticularly, this invention relates to reducing the amount of timeassociated with accessing data from tape.

Automated data storage libraries are known for providing cost effectivestorage and retrieval of large quantities of data. The data in automateddata storage libraries is typically stored on media of data storagecartridges that are, in turn, stored at storage slots or the like insidethe library in a fashion that renders the media, and its resident data,accessible for physical retrieval. Such data storage cartridges arecommonly termed “removable media.” Data storage cartridge media maycomprise any type of media on which data may be stored and which mayserve as removable media, including but not limited to magnetic media(such as magnetic tape or disks), optical media (such as optical tape ordisks), electronic media (such as PROM, EEPROM, flash PROM,CompactFlash™, Smartmedia™, Memory Stick™, etc.), or other suitablemedia. An example of a data storage cartridge that is widely employed inautomated data storage libraries for mass data storage is a magnetictape cartridge.

In addition to data storage media, automated data storage librariestypically comprise data storage drives that store data to, and/orretrieve data from, the data storage cartridge media. Further, automateddata storage libraries typically comprise I/O stations at which datastorage cartridges are supplied or added to, or removed from, thelibrary. The transport of data storage cartridges between data storageslots, data storage drives, and I/O stations is typically accomplishedby one or more accessors. Such accessors have grippers for physicallyretrieving the selected data storage cartridges from the storage slotswithin the automated data storage library and transporting suchcartridges to the data storage drives by moving, for example, in thehorizontal (X) and vertical (Y) directions.

As storage capacity increases, the amount of time and effort involvedwith accessing a desired segment of data rises as well. Not only isthere more data to sift through in order to find a desired segment ofdata, but accessing that data even after it has been located isincreasingly difficult as well.

SUMMARY

A computer-implemented method, according to one embodiment, includes:selecting a first tape to write a first copy of a first portion of datato, sending an instruction to write the first copy of the first portionof data to a first partition on the first tape, wherein the first tapehas at least the first partition and a second partition, selecting asecond tape that is different than the first tape to write a second copyof the first portion of data to, and sending an instruction to write thesecond copy of the first portion of data to a second partition on thesecond tape, wherein the second tape has at least a first partition andthe second partition. The first partition on each of the first andsecond tapes is closer to a beginning of the respective tape than thesecond partition on the respective tape.

A computer program product, according to another embodiment, includes acomputer readable storage medium having program instructions embodiedtherewith, the program instructions executable by a processor to causethe processor to: select, by the processor, a first tape to write afirst copy of a first portion of data to, send, by the processor, aninstruction to write the first copy of the first portion of data to afirst partition on the first tape, wherein the first tape has at leastthe first partition and a second partition, select, by the processor, asecond tape that is different than the first tape to write a second copyof the first portion of data to, and send, by the processor, aninstruction to write the second copy of the first portion of data to asecond partition on the second tape, wherein the second tape has atleast a first partition and the second partition. The first partition oneach of the first and second tapes is closer to a beginning of therespective tape than the second partition on the respective tape.

A computer program product, according to yet another embodiment,includes a computer readable storage medium having program instructionsembodied therewith, the program instructions executable by a processorto cause the processor to: receive, by the processor, a request to reada portion of data, determine, by the processor, whether the portion ofdata is located in a first partition of a tape loaded in a tape drive,send, by the processor, an instruction to read the portion of data fromthe first partition in response to determining that the portion of datais located in the first partition of the tape loaded in the tape drive,determine, by the processor, whether the portion of data is located in asecond partition of the tape loaded in the tape drive in response todetermining that the portion of data is not located in the firstpartition of the tape loaded in the tape drive, and send, by theprocessor, an instruction to read the portion of data from the secondpartition in response to determining that the portion of data is locatedin the second partition of the tape loaded in the tape drive. The firstpartition is closer to a beginning of the tape than the secondpartition.

Any of these embodiments may be implemented in a magnetic data storagesystem such as a tape drive system, which may include a magnetic head, adrive mechanism for passing a magnetic medium (e.g., recording tape)over the magnetic head, and a controller electrically coupled to themagnetic head.

Other aspects and embodiments of the present invention will becomeapparent from the following detailed description, which, when taken inconjunction with the drawings, illustrate by way of example theprinciples of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a perspective view of an automated data storage libraryaccording to one embodiment.

FIG. 2 is a perspective view of a storage frame from the data storagelibrary of FIG. 1.

FIG. 3 is a block diagram of an automated data storage library accordingto one embodiment.

FIG. 4 is a block diagram depicting a controller configuration accordingto one embodiment.

FIG. 5A is a front perspective view of a data storage drive according toone embodiment.

FIG. 5B is a rear perspective view of the data storage drive of FIG. 5A.

FIG. 6 is perspective view of a data storage cartridge having a cutawayportion, according to one embodiment.

FIG. 7 is a tiered data storage system according to one embodiment.

FIG. 8 is a block diagram of a data storage system according to oneembodiment.

FIG. 9 is a flowchart of a method according to one embodiment.

FIG. 10 is a tape having two partitions according to one embodiment.

FIG. 11 is a tape having two partitions according to one embodiment.

FIG. 12 is a tape having three partitions according to one embodiment.

FIG. 13 is a tape having three partitions according to one embodiment.

FIG. 14 is a flowchart of a method according to one embodiment.

FIG. 15 is a representative diagram of storing portions of data on atape having three partitions according to one embodiment.

DETAILED DESCRIPTION

The following description is made for the purpose of illustrating thegeneral principles of the present invention and is not meant to limitthe inventive concepts claimed herein. Further, particular featuresdescribed herein can be used in combination with other describedfeatures in each of the various possible combinations and permutations.

Unless otherwise specifically defined herein, all terms are to be giventheir broadest possible interpretation including meanings implied fromthe specification as well as meanings understood by those skilled in theart and/or as defined in dictionaries, treatises, etc.

It must also be noted that, as used in the specification and theappended claims, the singular forms “a,” “an” and “the” include pluralreferents unless otherwise specified.

The following description discloses several preferred embodiments ofmagnetic storage systems having reduced data access times, as well asoperation and/or component parts thereof. By implementing improvedprocesses of writing data and/or reading data according to the variousembodiments described herein, the amount of time associated withaccessing data from tape may desirably be reduced. Moreover, dataredundancy may also be achieved by the embodiments included herein,thereby also providing added safeguards against data loss

In one general embodiment, a computer-implemented method includes:selecting a first tape to write a first copy of a first portion of datato, sending an instruction to write the first copy of the first portionof data to a first partition on the first tape, wherein the first tapehas at least the first partition and a second partition, selecting asecond tape that is different than the first tape to write a second copyof the first portion of data to, and sending an instruction to write thesecond copy of the first portion of data to a second partition on thesecond tape, wherein the second tape has at least a first partition andthe second partition. The first partition on each of the first andsecond tapes is closer to a beginning of the respective tape than thesecond partition on the respective tape.

In another general embodiment, a computer program product includes acomputer readable storage medium having program instructions embodiedtherewith, the program instructions executable by a processor to causethe processor to: select, by the processor, a first tape to write afirst copy of a first portion of data to, send, by the processor, aninstruction to write the first copy of the first portion of data to afirst partition on the first tape, wherein the first tape has at leastthe first partition and a second partition, select, by the processor, asecond tape that is different than the first tape to write a second copyof the first portion of data to, and send, by the processor, aninstruction to write the second copy of the first portion of data to asecond partition on the second tape, wherein the second tape has atleast a first partition and the second partition. The first partition oneach of the first and second tapes is closer to a beginning of therespective tape than the second partition on the respective tape.

In yet another general embodiment, a computer program product includes acomputer readable storage medium having program instructions embodiedtherewith, the program instructions executable by a processor to causethe processor to: receive, by the processor, a request to read a portionof data, determine, by the processor, whether the portion of data islocated in a first partition of a tape loaded in a tape drive, send, bythe processor, an instruction to read the portion of data from the firstpartition in response to determining that the portion of data is locatedin the first partition of the tape loaded in the tape drive, determine,by the processor, whether the portion of data is located in a secondpartition of the tape loaded in the tape drive in response todetermining that the portion of data is not located in the firstpartition of the tape loaded in the tape drive, and send, by theprocessor, an instruction to read the portion of data from the secondpartition in response to determining that the portion of data is locatedin the second partition of the tape loaded in the tape drive. The firstpartition is closer to a beginning of the tape than the secondpartition.

FIGS. 1-2 illustrate an automated data storage library 10 which storesand retrieves data storage cartridges, containing data storage media(not shown), from multi-cartridge deep slot cells 100 and singlecartridge storage slots 16. An example of an automated data storagelibrary which has a similar configuration as that depicted in FIGS. 1-2,and may be implemented with some of the various approaches herein is theIBM 3584 UltraScalable Tape Library. Moreover, it should be noted thatreferences to “data storage media” herein refer to data storagecartridges, and for purposes of the present application, the two termsmay be used synonymously.

The library 10 of FIG. 1 comprises a left hand service bay 13, one ormore storage frames 11, and right hand service bay 14. As will bediscussed in further detail below, a frame may comprise an expansioncomponent of the library. Thus, storage frames may be added or removedto expand or reduce the size and/or functionality of the library.According to different approaches, frames may include additional storageslots, deep slot cells, drives, import/export stations, accessors,operator panels, etc.

FIG. 2 shows an exemplary embodiment of a storage frame 11, which actsas the base frame of the library 10. Moreover, the storage frame 11illustrated in FIG. 2 is contemplated to be a minimum configuration ofthe library 10, for which there is only a single accessor 18 (i.e.,there are no redundant accessors) and no service bay. However, in otherembodiments, a storage frame may include multiple robotic accessorsand/or service bays.

Looking to FIG. 2, the library 10 is arranged for accessing data storagemedia in response to commands from at least one external host system(not shown). The library 10 includes a plurality of storage slots 16 onfront wall 17 and a plurality of multi-cartridge deep slot cells 100 onrear wall 19, both of which may be used for storing data storagecartridges that may contain data storage media. According to oneapproach, the storage slots 16 are configured to store a single datastorage cartridge, and the multi-cartridge deep slot cells 100 may beconfigured to store more than one data storage cartridge.

With continued reference to FIG. 2, the storage frame 11 of the library10 also includes at least one data storage drive 15, e.g., for readingand/or writing data with respect to the data storage media.Additionally, a first accessor 18 may be used to transport data storagemedia between the plurality of storage slots 16, the multi-cartridgedeep slot cells, and/or the data storage drive(s) 15. According tovarious approaches, the data storage drives 15 may be optical diskdrives, magnetic tape drives, solid state drives having nonvolatilerandom access memory (NVRAM) such as Flash memory, or other types ofdata storage drives as are used to read and/or write data with respectto the data storage media.

As illustrated, the storage frame 11 may optionally include an operatorpanel or other user interface, such as a web-based interface, whichallows a user to interact with the library 10. The storage frame 11 mayalso optionally comprise an upper I/O station 24 and/or a lower I/Ostation 25, thereby allowing data storage cartridges to be added (e.g.,inserted) to the library inventory and/or removed from the librarywithout disrupting library operation. Furthermore, the library 10 mayhave one or more storage frames 11, each having storage slots 16,preferably accessible by the first accessor 18.

As described above, the storage frames 11 may be configured withdifferent components depending upon the intended function. Oneconfiguration of storage frame 11 may comprise storage slots 16 and/ormulti-cartridge deep slot cells 100, data storage drive(s) 15, and otheroptional components to store and retrieve data from the data storagecartridges. However, in another approach, a storage frame 11 may includestorage slots 16 and/or multi-cartridge deep slot cells 100 and no othercomponents. The first accessor 18 may have a gripper assembly 20, e.g.,for gripping one or more data storage media, in addition to having a barcode scanner or other reading system, such as a cartridge memory readeror similar system mounted on the gripper assembly 20, to “read”identifying information about the data storage media.

FIG. 3 depicts an automated data storage library 10, in accordance withone embodiment. As an option, the present automated data storage library10 may be implemented in conjunction with features from any otherembodiment listed herein, such as those described with reference to theother FIGS. Of course, however, such automated data storage library 10and others presented herein may be used in various applications and/orin permutations which may or may not be specifically described in theillustrative embodiments listed herein. Further, the automated datastorage library 10 presented herein may be used in any desiredenvironment. Thus FIG. 3 (and the other FIGS.) should be deemed toinclude any and all possible permutations

Referring now to FIG. 3, the automated data storage library 10 asdescribed in reference to FIGS. 1 and 2, is depicted according to oneembodiment. According to a preferred approach, the library 10 may employa controller, e.g., arranged as a distributed system of modules with aplurality of processor nodes.

In one approach, the library is controlled, not by a central controller,but rather, by a distributed control system for receiving logicalcommands and converting the commands to physical movements of theaccessor and gripper, and for operating the drives in accordance withthe desired physical movements. The distributed control system may alsoprovide logistical support, such as responding to host requests forelement status, inventory, library status, etc. The specific commands,the conversion of those commands to physical movements, and theoperation of the drives may be of a type known to those of skill in theart.

While the automated data storage library 10 has been described asemploying a distributed control system, various other approachesdescribed and/or suggested herein may be implemented in automated datastorage libraries regardless of control configuration, such as, but notlimited to, an automated data storage library having one or more librarycontrollers that are not distributed.

Referring still to FIG. 3, the library 10 may have one or more storageframes 11, a left hand service bay 13 and a right hand service bay 14.The left hand service bay 13 is shown with a first accessor 18, where,as discussed above, the first accessor 18 may include a gripper assembly20 and/or a bar code scanner (e.g., reading system) to “read”identifying information about the data storage media depending on thedesired embodiment. Furthermore, the right hand service bay 14 is shownhaving a second accessor 28, which includes a gripper assembly 30 andmay also include a reading system 32 to “read” identifying informationabout the data storage media.

According to one approach, in the event of a failure or otherunavailability of the first accessor 18, or its gripper assembly 20,etc., the second accessor 28 may perform some or all of the functions ofthe first accessor 18. Thus in different approaches, the two accessors18, 28 may share one or more mechanical paths, they may have completelyindependent mechanical paths, or combinations thereof. In one example,the accessors 18, 28 may have a common horizontal rail with independentvertical rails to travel therealong. Moreover, it should be noted thatthe first and second accessors 18, 28 are described as first and secondfor descriptive purposes only and this description is not meant to limiteither accessor to an association with either the left hand service bay13, or the right hand service bay 14.

In an exemplary embodiment which is in no way intended to limit theinvention, the first and second accessors 18, 28 may preferably movetheir grippers in at least two directions, called the horizontal “X”direction and vertical “Y” direction, e.g., to retrieve and grip,deliver and release, load and unload, etc. the data storage cartridge atthe storage slots 16, multi-cartridge deep slot cells 100, data storagedrives 15, etc.

With continued reference to FIG. 3, library 10 receives commands fromone or more host systems 40, 41, 42. The host systems 40, 41, 42, suchas host servers, communicate with the library directly, e.g., onconnection 80, through one or more control ports (not shown), or throughone or more data storage drives 15 on connections 81, 82. Thus, indifferent approaches, the host systems 40, 41, 42 may provide commandsto access particular data storage cartridges and move the cartridges,for example, between the storage slots 16 and the data storage drives15. The commands are typically logical commands identifying thecartridges or cartridge media, and/or logical locations for accessingthe media. Furthermore, it should be noted that the terms “commands” and“work requests” are used interchangeably herein to refer to suchcommunications from the host system 40, 41, 42 to the library 10 as areintended to result in accessing particular data storage media within thelibrary 10 depending on the desired approach.

According to one embodiment, the library 10 may be controlled by alibrary controller. Moreover, in various approaches, the librarycontroller may include a distributed control system receiving thelogical commands from hosts, determining the required actions, and/orconverting the actions to physical movements of the first and/or secondaccessor 18, 28. In another approach, the distributed control system mayhave a plurality of processor nodes, each having one or more computerprocessors. According to one example of a distributed control system, acommunication processor node 50 may be located in a storage frame 11.The communication processor node provides a communication link forreceiving the host commands, either directly or through the drives 15,via at least one external interface, e.g., coupled to connection 80.

Still referring to FIG. 3, the communication processor node 50 mayadditionally provide a communication link 70 for communicating with thedata storage drives 15. As illustrated, the communication processor node50 may preferably be located in the storage frame 11, e.g., close to thedata storage drives 15. Furthermore, one or more additional workprocessor nodes may be provided to form an exemplary distributedprocessor system, which may comprise, e.g., a work processor node 52located at first accessor 18, and that is coupled to the communicationprocessor node 50 via a network 60, 157. According to differentapproaches, each work processor node may respond to received commandsthat are broadcast thereto from any communication processor node, andthe work processor nodes may also direct the operation of the accessors,e.g., providing move commands. An XY processor node 55 may be providedand may be located at an XY system of first accessor 18. As illustrated,the XY processor node 55 is coupled to the network 60, 157, and isresponsive to the move commands, operating the XY system to position thegripper assembly 20.

Also, an operator panel processor node 59 may be provided at theoptional operator panel for providing an interface for communicatingbetween the operator panel and the communication processor node 50, thework processor nodes 52, 252, and the XY processor nodes 55, 255.

A network 60, for example comprising a common bus, is provided, couplingthe various processor nodes. The network may comprise a robust wiringnetwork, such as the commercially available Controller Area Network(CAN) bus system, which is a multi-drop network, having a standardaccess protocol and wiring standards, for example, as defined by CiA,the CAN in Automation Association, Am Weich Selgarten 26, D-91058Erlangen, Germany. Other networks, such as Ethernet, or a wirelessnetwork system, such as RF or infrared, may be employed in the libraryas is known to those of skill in the art. In addition, multipleindependent networks may also be used to couple the various processornodes.

As illustrated in FIG. 3, the communication processor node 50 is coupledto each of the data storage drives 15 of a storage frame 11, viacommunication links 70, and are thereby communicating with the drives 15and with host systems 40, 41, 42. Alternatively, the host systems 40,41, 42 may be directly coupled to the communication processor node 50,at connection 80 for example, or to control port devices (not shown)which connect the library to the host system(s) with a library interfacesimilar to the drive/library interface. As is known to those of skill inthe art, various communication arrangements may be employed forcommunication with the hosts and with the data storage drives. In theexample of FIG. 3, host connections 80 and 81 are intended to beEthernet and a SCSI bus, respectively, e.g., and may serve as hostconnections. However, connection 82 may be a bus. According to anexample, connection 82 may include a Fibre Channel bus which is a highspeed serial data interface, allowing transmission over greaterdistances than the SCSI bus systems.

According to some approaches, the data storage drives 15 may be in closeproximity to the communication processor node 50, and may employ a shortdistance communication scheme, such as Ethernet, or a serial connection,such as RS-422. Thus the data storage drives 15 may be individuallycoupled to the communication processor node 50 by communication links70. Alternatively, the data storage drives 15 may be coupled to thecommunication processor node 50 through one or more networks.

Furthermore, additional storage frames 11 may be provided, whereby eachis preferably coupled to the adjacent storage frame. According tovarious approaches, any of the additional storage frames 11 may includecommunication processor nodes 50, storage slots 16, data storage drives15, networks 60, etc.

Moreover, as described above, the automated data storage library 10 maycomprise a plurality of accessors. A second accessor 28, for example, isshown in a right hand service bay 14 of FIG. 3. The second accessor 28may include a gripper assembly 30 for accessing the data storage media,and an XY system 255 for moving the second accessor 28. The secondaccessor 28 may run on the same horizontal mechanical path as the firstaccessor 18, and/or on an adjacent (e.g., separate) path. Moreover theillustrative control system additionally includes an extension network200 which forms a network coupled to network 60 of the storage frame(s)11 and to network 157 of left hand service bay 13.

In FIG. 3 and the accompanying description, the first and secondaccessors are associated with the left hand service bay 13 and the righthand service bay 14 respectively. However, this is for illustrativepurposes and there may not be an actual association. Thus, according toanother approach, network 157 may not be associated with the left handservice bay 13 and network 200 may not be associated with the right handservice bay 14. Moreover, depending on the design of the library, it maynot be necessary to have a left hand service bay 13 and/or a right handservice bay 14 at all.

An automated data storage library 10 typically comprises one or morecontrollers to direct the operation of the automated data storagelibrary. Moreover, host computers and data storage drives typicallyinclude similar controllers. A library controller may take manydifferent forms and may comprise, for example, but is not limited to, anembedded system, a distributed control system, a personal computer, aworkstation, etc. The term “library controller” as used herein isintended in its broadest sense as a device that includes at least oneprocessor, and optionally further circuitry and/or logic, forcontrolling and/or providing at least some aspects of libraryoperations.

Referring now to FIG. 4, a typical controller 400 is shown with aprocessor 402, Random Access Memory (RAM) 403, nonvolatile memory 404,device specific circuits 401, and I/O interface 405. Alternatively, theRAM 403 and/or nonvolatile memory 404 may be contained in the processor402 as could the device specific circuits 401 and I/O interface 405. Theprocessor 402 may comprise, for example, an off-the-shelfmicroprocessor, custom processor, Field Programmable Gate Array (FPGA),Application Specific Integrated Circuit (ASIC), discrete logic, etc. TheRAM 403 is typically used to hold variable data, stack data, executableinstructions, etc.

According to various approaches, the nonvolatile memory 404 may compriseany type of nonvolatile memory such as, but not limited to, ElectricallyErasable Programmable Read Only Memory (EEPROM), flash Programmable ReadOnly Memory (PROM), battery backup RAM, hard disk drives, etc. However,the nonvolatile memory 404 is typically used to hold the executablefirmware and any nonvolatile data. Moreover, the I/O interface 405comprises a communication interface that allows the processor 402 tocommunicate with devices external to the controller. Examples maycomprise, but are not limited to, serial interfaces such as RS-232, USB(Universal Serial Bus) or Small Computer Systems Interface (SCSI). Thedevice specific circuits 401 provide additional hardware to enable thecontroller 400 to perform unique functions including, but not limitedto, motor control of a cartridge gripper. Moreover, the device specificcircuits 401 may include electronics that provide, by way of example butnot limitation, Pulse Width Modulation (PWM) control, Analog to DigitalConversion (ADC), Digital to Analog Conversion (DAC), etc. In addition,all or part of the device specific circuits 401 may reside outside thecontroller 400.

While the automated data storage library 10 is described as employing adistributed control system, the various approaches described and/orsuggested herein may be implemented in various automated data storagelibraries regardless of control configuration, including, but notlimited to, an automated data storage library having one or more librarycontrollers that are not distributed. Moreover, a library controller maycomprise one or more dedicated controllers of a library, depending onthe desired embodiment. For example, there may be a primary controllerand a backup controller. In addition, a library controller may compriseone or more processor nodes of a distributed control system. Accordingto one example, communication processor node 50 (e.g., of FIG. 3) maycomprise the library controller while the other processor nodes (ifpresent) may assist the library controller and/or may provide backup orredundant functionality. In another example, communication processornode 50 and work processor node 52 may work cooperatively to form thelibrary controller while the other processor nodes (if present) mayassist the library controller and/or may provide backup or redundantfunctionality. Still further, all of the processor nodes may comprisethe library controller. According to various approaches described and/orsuggested herein, a library controller may have a single processor orcontroller, or it may include multiple processors or controllers.

FIGS. 5A-5B illustrate the front 501 and rear 502 views of a datastorage drive 15, according to one embodiment. In the example depictedin FIGS. 5A-5B, the data storage drive 15 comprises a hot-swap drivecanister, which is in no way intended to limit the invention. In fact,any configuration of data storage drive may be used whether or not itincludes a hot-swap canister. As discussed above, a data storage drive15 is used to read and/or write data with respect to the data storagemedia, and may additionally communicate with a memory which is separatefrom the media, and is located within the cartridge. Thus, according toone approach, a data storage cartridge may be placed into the datastorage drive 15 at opening 503.

Furthermore, FIG. 6 illustrates an embodiment of a data storagecartridge 600 with a cartridge memory 610 shown in a cutaway portion ofthe Figure, which is in no way intended to limit the invention. In fact,any configuration of data storage cartridge may be used whether or notit comprises a cartridge memory. According to various approaches, mediaof the data storage cartridge media may include any type of media onwhich data may be stored, including but not limited to magnetic media,e.g., magnetic tape, disks, etc.; optical media, e.g., optical tape,disks, etc.; electronic media, e.g., PROM, EEPROM, flash PROM,CompactFlash™, Smartmedia™, Memory Stick™, etc.; etc., or other suitablemedia. Moreover, an example of a data storage cartridge that is widelyemployed in automated data storage libraries for mass data storage is amagnetic tape cartridge in which the media is magnetic tape.

Now referring to FIG. 7, a storage system 700 is shown according to oneembodiment. Note that some of the elements shown in FIG. 7 may beimplemented as hardware and/or software, according to variousembodiments. In some approaches, the storage system 700 may beimplemented in an automated data storage library such as that shown inFIGS. 1-2. In other approaches, an automated data storage library suchas that shown in FIGS. 1-2 may be a tier of the storage system 700.

The storage system 700 may include a storage system manager 712 forcommunicating with a plurality of media on at least one higher storagetier 702 and at least one lower storage tier 706. The higher storagetier(s) 702 preferably may include one or more random access and/ordirect access media 704, such as hard disks in hard disk drives (HDDs),nonvolatile memory (NVM), solid state memory in solid state drives(SSDs), flash memory, SSD arrays, flash memory arrays, etc., and/orothers noted herein or known in the art. The lower storage tier(s) 706may preferably include one or more lower performing storage media 708,including sequential access media such as magnetic tape in tape drivesand/or optical media, slower accessing HDDs, slower accessing SSDs,etc., and/or others noted herein or known in the art. One or moreadditional storage tiers 716 may include any combination of storagememory media as desired by a designer of the system 700. Also, any ofthe higher storage tiers 702 and/or the lower storage tiers 706 mayinclude some combination of storage devices and/or storage media.

The storage system manager 712 may communicate with the storage media704, 708 on the higher storage tier(s) 702 and lower storage tier(s) 706through a network 710, such as a storage area network (SAN), as shown inFIG. 7, or some other suitable network type. The storage system manager712 may also communicate with one or more host systems (not shown)through a host interface 714, which may or may not be a part of thestorage system manager 712. The storage system manager 712 and/or anyother component of the storage system 700 may be implemented in hardwareand/or software, and may make use of a processor (not shown) forexecuting commands of a type known in the art, such as a centralprocessing unit (CPU), a field programmable gate array (FPGA), anapplication specific integrated circuit (ASIC), etc. Of course, anyarrangement of a storage system may be used, as will be apparent tothose of skill in the art upon reading the present description.

In more embodiments, the storage system 700 may include any number ofdata storage tiers, and may include the same or different storage memorymedia within each storage tier. For example, each data storage tier mayinclude the same type of storage memory media, such as HDDs, SSDs,sequential access media (tape in tape drives, optical disk in opticaldisk drives, etc.), direct access media (CD-ROM, DVD-ROM, etc.), or anycombination of media storage types. In one such configuration, a higherstorage tier 702, may include a majority of SSD storage media forstoring data in a higher performing storage environment, and remainingstorage tiers, including lower storage tier 706 and additional storagetiers 716 may include any combination of SSDs, HDDs, tape drives, etc.,for storing data in a lower performing storage environment. In this way,more frequently accessed data, data having a higher priority, dataneeding to be accessed more quickly, etc., may be stored to the higherstorage tier 702, while data not having one of these attributes may bestored to the additional storage tiers 716, including lower storage tier706. Of course, one of skill in the art, upon reading the presentdescriptions, may devise many other combinations of storage media typesto implement into different storage schemes, according to theembodiments presented herein.

According to some embodiments, the storage system (such as 700) mayinclude logic configured to receive a request to open a data set, logicconfigured to determine if the requested data set is stored to a lowerstorage tier 706 of a tiered data storage system 700 in multipleassociated portions, logic configured to move each associated portion ofthe requested data set to a higher storage tier 702 of the tiered datastorage system 700, and logic configured to assemble the requested dataset on the higher storage tier 702 of the tiered data storage system 700from the associated portions. Of course, this logic may be implementedas a method on any device and/or system or as a computer programproduct, according to various embodiments.

As previously mentioned, the amount of time and effort involved withaccessing a desired segment of data rises as storage capacity increases.Not only is there more data to sift through in order to find a desiredsegment of data, but accessing that data, even after it has beenlocated, is increasingly difficult as well. This is particularly truefor data stored in linear media such as magnetic tape. Although magnetictape is a relatively inexpensive storage medium, data access times formagnetic tape is slower than for other media types.

In sharp contrast, various embodiments described herein may be able toreduce the amount of time associated with accessing data from tape.Moreover, data redundancy may also be achieved by various embodimentsincluded herein, thereby also safeguarding against data loss.

Referring momentarily to FIG. 8, a tape storage system 800 isillustrated in accordance with one embodiment. As an option, the presentsystem 800 may be implemented in conjunction with features from anyother embodiment listed herein, such as those described with referenceto the other FIGS. However, such system 800 and others presented hereinmay be used in various applications and/or in permutations which may ormay not be specifically described in the illustrative embodiments listedherein. Further, the system 800 presented herein may be used in anydesired environment. Thus FIG. 8 (and the other FIGS.) may be deemed toinclude any possible permutation.

As shown, tape storage system 800 includes a host location 802 which iscoupled to a disk based storage location 804 and a tape library 806,e.g., which may include any of the features described with reference toFIGS. 1-6. The host location 802 in the present embodiment includes atape application 808 having a tracking database 810. In some approaches,tape application 808 may be used to control the tape library 806, e.g.,transfer and/or access data stored in the tape library 806. For example,the tape application 808 may record the location of data on tapecartridges into the tracking database 810. Moreover, in some approaches,the tracking database 810 may be used to implement any one or more ofthe processes included below in method 900 and/or 1400.

Moreover, tape library 806 includes tape drives 812 which are coupled tomedium changer 814, which may be an accessor (e.g., see accessor 18 ofFIG. 1). Each of the tape drives 812 preferably include a tape headwhich is able to write data to and/or read data from the tape stored ina tape cartridge 816 when positioned in one of the tape drives 812.Medium changer 814 may be used to coordinate which tape cartridge 816 isin each of the tape drives 812, e.g., according to instructions receivedfrom the host location 802 and/or a controller of the tape library 806.Furthermore, tape cartridges 816 are stored collectively in pools, whichmay be physical pools, but are preferably logical pools. According tothe present embodiment, system 800 is shown as having a primary pool anda secondary pool which may be used to classify the tape cartridges 816according to any desired storage configuration. Moreover, the tapeapplication 808 may be used to manage the primary and secondary pools.

In a preferred approach, data is replicated such that one copy thereofresides on a cartridge in the primary pool while another copy of thedata resides on a cartridge in the secondary pool. This provides dataredundancy for such things as disaster recovery. However, pools may beprovided, and tape allocated thereto, for any desired purpose.

According to some approaches, the tape library 806 may be used to storedata received from the disk based storage location 804. In other words,the tape library 806 may be used to archive data formerly stored at thedisk based storage location 804. According to one example, which is inno way intended to limit the invention, as data stored on the disk basedstorage location 804 becomes “colder” (e.g., has an access and/or updaterate slower than “hot” data), the host location 802 may decide totransfer such data to the tape library 806 for archival storage, e.g.,to make room at the disk based storage location 804 for “hotter” data.

Looking to FIG. 9, a method 900 includes an improved process for writingdata in accordance with one embodiment. As an option, the present method900 may be implemented in conjunction with features from any otherembodiment listed herein, such as those described with reference to theother FIGS., such as FIG. 8. However, such method 900 and otherspresented herein may be used in various applications and/or inpermutations which may or may not be specifically described in theillustrative embodiments listed herein. Further, the method 900presented herein may be used in any desired environment. Thus FIG. 9(and the other FIGS.) may be deemed to include any possible permutation.

Again, method 900 includes a process for writing data that may be usedto reduce the amount of time associated with accessing particular datafrom tape (e.g., see method 1400 below). As data to be written to tapeis received, it may be partitioned into portions before being writtenout to tape. Accordingly, optional operation 902 includes dividingreceived data into portions. The characteristics of the portionsthemselves may be determined based on predetermined and/ordynamically-determined criteria, such as size (e.g., each potion havinga certain amount of data therein), a temperature of the data (e.g., hotdata that is accessed more frequently v. cold data that is accessed lessfrequently), an amount of data received, user preference, etc.,depending on the desired embodiment.

Once the data has been divided into portions, operation 904 of method900 includes selecting a first tape to write a first copy of a firstportion of data to. Moreover, operation 906 includes sending aninstruction to write a first copy of a first portion of data to a firstof at least two partitions on the first tape. It is preferred that thefirst tape selected is one that is already positioned in a tape drive.As mentioned above, a tape drive may include a tape head which is ableto write data to and/or read data from the tape of a tape cartridge whenthe tape cartridge itself is mounted in one of the tape drives. Thus, byselecting a first tape in operation 904 which is already positioned in atape drive, the amount of time to perform operations 904 and 906 maydesirably be reduced. However, the selected first tape may be any one ofthe tapes included in a given tape library.

As alluded to above, the first tape preferably has at least a firstpartition and a second partition, and optionally one or more additionalpartitions. It is also preferred, but in no way required, that all tapesincluded in a tape library from which the selection of operation 904 isperformed have at least a first and second partition. Referringmomentarily to FIG. 10, a representation of a tape 1000 is depicted ashaving two physical partitions, namely a first partition 1002 and asecond partition 1004 separated by a guard gap 1005, according to anillustrative embodiment. First and second partitions 1002, 1004 may beachieved by modifying the internal formatting indicators of the tapeitself and/or in a cartridge memory (e.g., see 610 of FIG. 6), andwriting separately to each partition on the corresponding side of theguard gap 1005, which prevents overwriting of data from one partition tothe other. However, any other process of achieving segmentation alongthe tape which would be apparent to one skilled in the art upon readingthe present description may be used. For instance, a function ofperformance scaling (e.g., capacity scaling) may be used to contain datain specified fractions (partitions) of the tape.

As shown, the first partition 1002 on the tape 1000 is closer to abeginning of tape (BOT) 1006 than the second partition 1004. Moreover,the second partition 1004 is closer to an end of tape (EOT) 1008 thanthe first partition 1002. It follows that the BOT 1006 is located at anopposite end of the tape 1000 than the EOT 1008. The BOT 1006 may beidentified as the portion of the tape that is first threaded through atape drive from a cartridge that is loaded in the tape drive, while theEOT 1008 may be identified as the opposite end of tape, e.g., the endthat remains fixed to the tape reel 1010 in the cartridge (not shown),as would be appreciated by one skilled in the art upon reading thepresent description. It should be noted that although tape 1000 is shownas having two partitions 1002, 1004, tapes may include additionalpartitions in other embodiments, e.g., as shown in FIGS. 12-13 below.

In use, data may be written to and read from the first partition 1002using conventional techniques. Data may also be written to and read fromthe second portion 1004. Thus, each partition may be treated effectivelyas a separate tape, whereby a tape wrap for a given partition extendsbetween the respective end region (BOT or EOT) of the tape to the guardgap 1005.

Data stored in the first partition 1002 may be accessed more quicklythan data stored in the second partition 1004 because the data stored inthe first partition 1002 is located closer to the BOT 1006. Accordingly,the data stored in the first partition 1002 may be accessed by unrollinga lesser amount of tape from the reel than to access data stored in thesecond partition 1004 which is located farther from the BOT 1006.Accordingly, read requests may be performed according to a hierarchywhich outlines the access times associated with reading data indifferent locations within a tape library, as will be described infurther detail below (e.g., see FIG. 14 and Table 1 below).

The first and second partitions 1002, 1004 illustrated in FIG. 10 haveabout equal dimensions. For example, the first and second partitions1002, 1004 have lengths L₁, L₂ measured along a longitudinal axis 1014of the tape 1000 which are about equal. However, the lengths of eachpartition may be set to any desired value. Particularly, although thetwo or more partitions included on each of the tapes in a tape librarymay each have about equal dimensions (e.g., width, length, etc.), insome approaches, the dimensions of the partitions included on a giventape may differ. Looking to FIG. 11, the partitions 1152, 1154 havedifferent lengths L₃, L₄ measured along a longitudinal axis 1014 of thetape 1150 which is perpendicular to the cross-track direction 1012.Specifically, the length L₃ of the first partition 1152 is shorter thanthe length L₄ of the second partition 1154. It follows that because thelengths L₃, L₄ of the partitions 1152, 1154 are different, each of thepartitions 1152, 1154 may be able to store different amounts of datatherein. For instance, the first partition 1152 may be able to storeabout 60 GB of data, while the second partition 1154 may be able tostore about 200 GB of data. By reducing L₃ and thereby the amount oftape available to store data in the first partition 1152 compared to thesecond partition 1154, the second partition 1154 is consequently able tostore more data than the first partition 1152 is able to. In someapproaches, the data capacity of the first partition 1152 may be reducedwhile the data capacity of the second partition 1154 may be increased inorder to further reduce the access time associated with reading datafrom the first partition 1152. As the first partition 1152 is shiftedcloser towards the BOT, the time to access data stored therein may beeven further reduced, particularly in view of the second partition 1154.

It follows that the dimensions of the partitions included on a giventape may be adjusted according to the desired embodiment. In someembodiments, the dimensions of the partitions included on each tape in alibrary may be about equal. However, in other embodiments the dimensionsof the partitions included on each respective tape in a library may vary(e.g., as shown in FIG. 11), or the dimensions of the partitions mayvary between each of the tapes in the library.

Referring again to method 900, implementing data redundancy is desirablein order to prevent total data loss, e.g., in the event that a firstcopy of the data is deleted, overwritten, corrupted, etc. Accordingly,operation 908 includes selecting a second tape that is different thanthe first tape to write a second copy of the first portion of data to.By writing a second copy of the first portion of data to a differenttape than the first tape where the first copy of the first portion ofdata is stored, greater redundancy is achieved than if the first andsecond copies of the first portion of data were written to the sametape. Accordingly, if one of the tapes having the first copy of thefirst portion of data is temporarily, permanently, etc., unavailable,then the other tape having the second copy of the first portion of datamay be used to provide access to the data.

Any desired criteria may be used to select the second tape.

As previously mentioned, it is preferred that the second tape selectedis one that is already loaded in a tape drive to reduce the amount oftime to write the second copy of the first portion of data. According toone approach, a tape library may have multiple tape drives (e.g., asseen in FIG. 10). Thus, operation 904 may include selecting a tape inone of the tape drives, while operation 908 includes selecting adifferent tape in a different one of the tape drives. However, again theselected second tape may be any one of the tapes included in a giventape library, whether loaded in a drive or not.

Moreover, it should be noted that the first and/or second tapes arepreferably selected in a pseudo-random manner. In other words, themanner by which the first and/or second tapes are selected to have therespective first and second copies of the first portion of data storedthereon is done pseudo-randomly. Thus, as subsequent portions of dataare stored in tapes included in a tape library using the operations ofmethod 900, the portions of data may be about evenly distributed amongthe tapes included in the library, because implementing a pseudo-randomselection process may achieve an about even distribution of portions ofdata across the library as would be appreciated by one skilled in theart upon reading the present description.

With continued reference to FIG. 9, operation 910 includes sending aninstruction to write the second copy of the first portion of data to asecond partition on the second tape. Like the first tape, the secondtape preferably has at least a first partition and a second partition,e.g., as shown in FIGS. 10-11 above. Moreover, it follows that tapedrives which are able to implement such data redundancy on partitionedtapes, while also tracking the physical data location on each of thetapes are preferred, e.g., such as IBM TS1150 tape drives, which may beimplemented with any of the embodiments described herein.

In some embodiments, a tape may have even more than two partitions.Looking to FIGS. 12-13, tapes 1200, 1350 are shown as having threepartitions. In FIG. 12, tape 1200 has first, second and third partitions1202, 1204, 1206 respectively. The first partition 1202 on the tape 1200is closer to the BOT 1208 than the second and third partitions 1204,1206, while the second partition 1204 is closer to the BOT 1208 than thethird partition 1206. Moreover, the third partition 1206 is closer tothe EOT 1210 than the first and second partitions 1202, 1204, while thesecond partition 1204 is closer to the EOT than the first partition1202.

Again, the BOT 1208 may be identified as the end of the tape that isfirst threaded through a tape drive from a cartridge that is loaded inthe tape drive, while the EOT 1210 may be identified as the other end ofthe tape, e.g., that remains fixed to the tape reel 1214 in thecartridge (not shown), as would be appreciated by one skilled in the artupon reading the present description. It follows that data stored in thefirst partition 1202 may be accessed more quickly than data accessed inthe second or third partitions 1204, 1206, while data stored in thesecond partition 1204 may be accessed more quickly than data stored inthe third partition 1206. Moreover, the first, second and thirdpartitions 1352, 1354, 1356 of tape 1350 in FIG. 13 are shown as havingdifferent lengths L₅, L₆, L₇ respectively, according to one embodiment.

Accordingly, in some approaches, a third copy of a portion of data maybe stored to one of the partitions on a third tape, e.g., for addedredundancy. Thus, a third copy of a portion of data may be recovereddespite the first and second copies being corrupted, deleted,overwritten, etc. According to an example, a user may choose to make athird copy of particularly important data in order to reduce the chanceof losing the data.

Returning to method 900, optional operation 912 includes selecting athird tape that is different than the first and second tapes to write athird copy of the first portion of data to. As previously mentioned, thethird tape may be chosen in a pseudo-random manner. However, it ispreferred that the third tape is already positioned in a drive.Therefore, in some approaches the tapes already positioned in drives maybe given preference over those located elsewhere in a tape library(e.g., in storage slots). Moreover, it is again preferred that the thirdtape is a different tape than the first and second tapes. Alternatively,if the third copy of the first data portion were written to a thirdpartition of the first or second tape selected in operations 904, 908respectively, the portion of data would not be afforded additionalredundancy.

Furthermore, optional operation 914 includes sending an instruction towrite the third copy of the first portion of data to a third partitionon the third tape. It should be noted that the operations of method 900are in no way intended to limit the order in which copies of a portionof data is stored on tape. For instance, a first copy of a first portionof data may first be stored in a third partition of a different tape,while a second copy of the first portion of data may be stored on afirst partition of a given tape, and a third copy of the first portionof data may be stored on a second partition of yet another tape, or anycombination thereof depending on the desired embodiment. Moreover, itshould also be noted that second, third, etc. copies of a given portionof data may be stored on partitions of different tapes despite the tapehaving the first copy of the portion of data being ejected from a tapedrive. As a tape, or portions thereof, are filled, the tape may beejected from a tape drive in order to load a different tape to use forperforming subsequent write operations and/or a read operation as wouldbe appreciated by one skilled in the art upon reading the presentdescription.

As described above, data stored in different partitions of tape may havedifferent access times associated therewith. For instance, data storedin a first partition may be accessed more quickly than data stored in asecond partition or a third partition because the data stored in thefirst partition is located closer to the BOT. Accordingly, the datastored in the first partition may be accessed by unrolling a lesseramount of tape from the reel than to access data stored in the secondand third partitions which are located farther from the BOT. Moreover,data stored in the second partition may be accessed more quickly thandata stored in the third partition for similar reasons.

It follows that when a read request is received for a given portion ofdata that is stored in more than one location (e.g., there are redundantcopies) in a tape library, where the data is read from may have aneffect on the amount of time it takes to successfully perform the readrequest. Accordingly, read requests may be performed according to ahierarchy which incorporates the different access times associated withreading data that is stored in different locations within a tape libraryas well as the present location of a given tape in the tape library.

Looking to Table 1, the relative data access times corresponding to eachpartition of a three-partition tape depending on whether the tape islocated in a tape drive or not are presented.

TABLE 1 Loaded in Tape Drive Not Loaded in Tape Drive First PartitionFastest Slow Second Partition Faster Slower Third Partition Fast Slowest

As shown, data access times for a tape having first, second and thirdpartitions (e.g., as shown in FIG. 12) which is already loaded in a tapedrive is shorter than data access times for a three-partition tapepositioned elsewhere in a storage library (e.g., in a storage slot).Moreover, data located in the first partition has a faster data accesstime than data located in the second or third partitions because thefirst partition is positioned closer to the BOT, as previouslydescribed. Thus, it is preferred that read requests are performed usingtapes already located in tape drives, while tapes not already located ina tape drive may be used should the requested data not be located in atape already loaded in a tape drive.

Now referring to FIG. 14, a flowchart of a computer-implemented method1400 for performing a read request is shown according to one embodiment.The method 1400 may be performed in accordance with the presentinvention in any of the environments depicted in FIGS. 1-13 and Table 1,among others, in various embodiments. Of course, more or less operationsthan those specifically described in FIG. 14 may be included in method1400, as would be understood by one of skill in the art upon reading thepresent descriptions.

Each of the steps of the method 1400 may be performed by any suitablecomponent of the operating environment. For example, in variousembodiments, the method 1400 may be partially or entirely performed by acontroller, a processor, etc., or some other device having one or moreprocessors therein. The processor, e.g., processing circuit(s), chip(s),and/or module(s) implemented in hardware and/or software, and preferablyhaving at least one hardware component may be utilized in any device toperform one or more steps of the method 1400. Illustrative processorsinclude, but are not limited to, a central processing unit (CPU), anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA), etc., combinations thereof, or any other suitablecomputing device known in the art.

As shown in FIG. 14, operation 1402 of method 1400 includes receiving arequest to read a portion of data from tape. The request may be receivedfrom a user, a host location (e.g., see 1002 of FIG. 10), a differentdata-storage tier itself, etc., depending on the embodiment.

After receiving the read request, method 1400 proceeds to decision 1404which includes determining whether the portion of data is located in afirst partition of a tape loaded in a tape drive. Referring back toTable 1, data stored in the first partition of a tape already located(e.g., loaded) in a tape drive has the fastest access time compared toother partitions and/or tapes in a library not already located in a tapedrive. Therefore, it is desirable that method 1400 first determineswhether the data corresponding to a read request is located in a firstpartition of a tape loaded in a tape drive. Moreover, it should be notedthat an embodiment may include more than one tape drive. For example,FIG. 12 includes several tape drives. Accordingly, decision 1404 mayinvolve determining whether the requested portion of data is located ina first partition of any one of the tapes located in any one of the tapedrives in a given tape library.

As shown, method 1400 proceeds to operation 1406 in response todetermining that the portion of data is located in the first partitionof any one of the tapes located in any one of the tape drives in a giventape library. Operation 1406 includes sending an instruction to read theportion of data from the first partition.

Alternatively, decision 1408 is performed in response to determiningthat the portion of data is not located in the first partition of anyone of the tapes located in any one of the tape drives in a given tapelibrary. Decision 1408 includes determining whether the portion of datais located in a second partition of any one of the tapes located in anyone of the tape drives in a given tape library. Again, Table 1 outlinesthat data stored in the second partition of a tape already located(e.g., loaded) in a tape drive has a faster access time compared toother tapes not located in a tape drive already. This is at leastpartially due to the fact that accessing data on a tape not alreadyloaded in a tape drive involves accessing the tape, loading it in adrive, and then locating the data, thereby increasing the data accesstime.

Operation 1410 includes sending an instruction to read the portion ofdata from the second partition in response to determining that theportion of data is located in the second partition of any one of thetapes located in any one of the tape drives in a given tape library.However, method 1400 alternatively progresses to decision 1412 inresponse to determining that the portion of data is not located in thesecond partition of any one of the tapes located in any one of the tapedrives in a given tape library. Then, decision 1412 includes determiningwhether the portion of data is located in a third partition of any oneof the tapes located in any one of the tape drives in a given tapelibrary.

Operation 1414 sends an instruction to read the portion of data from thethird partition in response to determining that the portion of data islocated in the third partition of any one of the tapes located in anyone of the tape drives in a given tape library.

Further operations may be performed to determine if any partition of atape loaded in a drive has the desired portion of data, and if so, thatdata is used. If not, the method proceeds to decision 1416. As shown,decision 1416 includes determining whether the portion of data islocated in a first partition of a tape in a tape library. Again, Table 1illustrates that if a portion of data is not located in a tape alreadylocated (e.g., loaded) in a tape drive, the next lowest data access timeis provided by selecting a tape having the data in the first partition,where the tape is in a storage location of the tape library.

Accordingly, an instruction to load a tape having the portion of datalocated in a first partition thereof into the tape drive is sent inresponse to determining that the portion of data is located in the firstpartition of the tape in the tape library. See operation 1418. Moreover,operation 1420 includes sending an instruction to read the portion ofdata from the first partition of the tape loaded from the tape library.

Returning to decision 1416, method 1400 proceeds to decision 1422 inresponse to determining that the portion of data is not located in thefirst partition of any one of the tapes in the tape library. There,decision 1422 includes determining whether the portion of data islocated in a second partition of any one of the tapes in the tapelibrary. An instruction to load a tape having the portion of datalocated in a second partition thereof into a tape drive is sent inresponse to determining that the portion of data is located in thesecond partition of any one of the tapes in the tape library. Seeoperation 1424. Furthermore, operation 1426 includes sending aninstruction to read the portion of data from the second partition of thetape loaded from the tape library.

Should it be determined that the portion of data is not located in thesecond partition of any one of the tapes in the tape library, method1400 continues on to decision 1428 which determines whether the portionof data is located in a third partition (or any other partition) of anyone of the tapes in the tape library. Moreover, operation 1430 includessending an instruction to load a tape having the portion of data locatedin a third (or other) partition thereof into a tape drive in response todetermining that the portion of data is located in the third partitionof any one of the tapes in the tape library. Furthermore, operation 1432includes sending an instruction to read the portion of data from thethird (or other) partition of the tape loaded from the tape library.

Returning to decision 1428, method 1400 is illustrated as proceeding tooperation 1434 in response to determining that the portion of data islocated in the third partition of any one of the tapes in the tapelibrary. According to one approach, operation 1434 may include returninga notice that the read request was not able to be performed. Accordingto another approach, operation 1434 may inform a host that the requestedportion of data was not found in the tape library, e.g., so it may besearched for elsewhere such as in a disk based storage location, aremote data repository, etc.

As alluded to above, should any of the tapes included in the tapelibrary include any additional partitions (e.g., a fourth partition, afifth partition, etc.), method 1400 may further include determiningwhether the requested portion of data is located in any of theadditional partitions before returning a failed read request notice.

It should also be noted that method 1400 is shown returning to operation1402 in response to sending an instruction to read the portion of datafrom the partition in which it was found. As a result, method 1400 maywait to receive a subsequent read request, but is in no way limitedthereto.

Referring now to FIG. 15, a representative diagram 1500 of an in-useembodiment is provided, which is in no way intended to limit theinvention, but rather is provided by way of example only. As shown, acopy of each portion of data is located in each of the three partitions.For example, a first copy of the first portion of data Data 1 is locatedin the first partition Partition 1 of the first tape in cartridge 01Cart01, while a second copy of the first portion of data Data 1 islocated in the second partition Partition 2 of the second tape incartridge 02 Cart02 and the third copy of the first portion of data Data1 is located in the third partition Partition 3 of the third tape incartridge 03 Cart03.

However, the tape on which each copy of the data portion is stored ispreferably selected in a pseudo-random manner. Thus, the number of thecopy and tape on which it is stored may not have a linear relationshipas seen in the previous example. According to another example, a firstcopy of the second portion of data Data 2 is located in the firstpartition Partition 1 of the second tape Cart02, while a second copy ofthe second portion of data Data 2 is located in the second partitionPartition 2 of the first tape Cart01 and the third copy of the secondportion of data Data 2 is located in the third partition Partition 3 ofthe fourth tape in cartridge 04 Cart04.

Although the in-use embodiment of FIG. 15 shows data written to each ofthe three partitions in each of the tapes even though none of thepartitions themselves have been filled, it should be noted that it ispreferred that the first partition on a given tape is written in fullbefore any data is written to any subsequent partition of the giventape. Thus, in some approaches a tape may not be selectable to have aportion of data written to a second, third, etc. partition thereofbefore the leading partitions are filled. According to an example, atape with only a partially filled first partition may not be selected tohave a copy of a given data portion written to the third partitionthereof. However, after the first and second partitions have beenwritten in full, the tape may be selected to have a copy of a given dataportion written to the third partition thereof.

In some approaches, one or more portions of data may be assigned to agiven partition of a given tape but not actually written until later.The assigned data may be stored in memory and the write thereofperformed at a later time, e.g., when the target tape becomes loaded andmounted in a drive. According to an example, which is in no way intendedto limit the invention, a tape may be pseudo-randomly selected to storea copy of a portion of data in a second partition of the tape. However,the first partition of the tape may not yet be filled, therebypreventing data from actually being written to the second partition ofthe tape when selected. Accordingly, the operation of writing theportion of data to the second partition may be queued in memory, e.g.,to actually be performed after the first partition of the tape iswritten in full, thereby allowing data to be written to the secondpartition of the tape.

It follows that various embodiments described herein may be able toreduce the amount of time associated with accessing data from tape byimplementing improved processes of writing data thereto and/or readingdata therefrom.

Tape access times are typically faster if the location of data is closeto the BOT (at least compared to data closer to the EOT), particularlyon single reel tape cartridges. However, most conventional storagesystems are not aware of the tape position where particular data hasbeen written to because of its difficulty to implement and maintain. Insharp contrast, the various embodiments described and suggested hereinmay be able to achieve “partition-aware” embodiments which are able toselect tape cartridges for writing copies of a given portion of data indifferent partitions on specific regions of the tape. Moreover, asmentioned above, it is preferred that tape drives and/or tapeapplications which support the longitudinal partitioning as describedherein are used.

Moreover, data redundancy may also be achieved by the embodimentsincluded herein, thereby also providing added safeguards against dataloss.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

Moreover, a system according to various embodiments may include aprocessor and logic integrated with and/or executable by the processor,the logic being configured to perform one or more of the process stepsrecited herein. By integrated with, what is meant is that the processorhas logic embedded therewith as hardware logic, such as an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA), etc. By executable by the processor, what is meant is that thelogic is hardware logic; software logic such as firmware, part of anoperating system, part of an application program; etc., or somecombination of hardware and software logic that is accessible by theprocessor and configured to cause the processor to perform somefunctionality upon execution by the processor. Software logic may bestored on local and/or remote memory of any memory type, as known in theart. Any processor known in the art may be used, such as a softwareprocessor module and/or a hardware processor such as an ASIC, a FPGA, acentral processing unit (CPU), an integrated circuit (IC), a graphicsprocessing unit (GPU), etc.

A data processing system suitable for storing and/or executing programcode may include at least one processor, which may be or be part of acontroller, coupled directly or indirectly to memory elements through asystem bus, such as controller 400 of FIG. 4. The memory elements caninclude local memory employed during actual execution of the programcode, such as nonvolatile memory 404 of FIG. 4, bulk storage, and cachememories which provide temporary storage of at least some program codein order to reduce the number of times code must be retrieved from bulkstorage during execution.

It will be clear that the various features of the foregoing systemsand/or methodologies may be combined in any way, creating a plurality ofcombinations from the descriptions presented above.

It will be further appreciated that embodiments of the present inventionmay be provided in the form of a service deployed on behalf of acustomer to offer service on demand.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of an embodiment of the presentinvention should not be limited by any of the above-described exemplaryembodiments, but should be defined only in accordance with the followingclaims and their equivalents.

What is claimed is:
 1. A computer-implemented method, comprising:selecting a first tape to write a first copy of a first portion of datato; sending an instruction to write the first copy of the first portionof data to a first partition on the first tape, wherein the first tapehas at least the first partition and a second partition; selecting asecond tape that is different than the first tape to write a second copyof the first portion of data to; and sending an instruction to write thesecond copy of the first portion of data to a second partition on thesecond tape, wherein the second tape has at least a first partition andthe second partition, wherein the first partition on each of the firstand second tapes is closer to a beginning of the respective tape thanthe second partition on the respective tape.
 2. The computer-implementedmethod as recited in claim 1, wherein the first and second partitions oneach of the first and second tapes have an about equal length measuredalong a longitudinal axis of each of the respective tapes.
 3. Thecomputer-implemented method as recited in claim 1, wherein the first andsecond partitions on each of the first and second tapes have differentlengths measured along a longitudinal axis of each of the respectivetapes.
 4. The computer-implemented method as recited in claim 1, whereinthe first and second partitions on each of the first and second tapeshave different lengths measured along a longitudinal axis of each of therespective tapes.
 5. The computer-implemented method as recited in claim1, wherein selecting the first and second tapes is done pseudo-randomly.6. The computer-implemented method as recited in claim 1, comprising:selecting a third tape that is different than the first and second tapesto write a third copy of the first portion of data to; and sending aninstruction to write the third copy of the first portion of data to athird partition on the third tape, wherein the third tape has at least afirst partition, second partition and the third partition, wherein thefirst partition on the third tape is closer to a beginning of therespective tape than the second and third partitions on the respectivetape, wherein the second partition on the third tape is closer to thebeginning of the respective tape than the third partition on therespective tape.
 7. A computer program product comprising a computerreadable storage medium having program instructions embodied therewith,the program instructions executable by a processor to cause theprocessor to: select, by the processor, a first tape to write a firstcopy of a first portion of data to; send, by the processor, aninstruction to write the first copy of the first portion of data to afirst partition on the first tape, wherein the first tape has at leastthe first partition and a second partition; select, by the processor, asecond tape that is different than the first tape to write a second copyof the first portion of data to; and send, by the processor, aninstruction to write the second copy of the first portion of data to asecond partition on the second tape, wherein the second tape has atleast a first partition and the second partition, wherein the firstpartition on each of the first and second tapes is closer to a beginningof the respective tape than the second partition on the respective tape.8. The computer program product of claim 7, wherein the first and secondpartitions on each of the first and second tapes have an about equallength measured along a longitudinal axis of each of the respectivetapes.
 9. The computer program product of claim 7, wherein the first andsecond partitions on each of the first and second tapes have differentlengths measured along a longitudinal axis of each of the respectivetapes.
 10. The computer program product of claim 7, wherein the firstand second partitions on each of the first and second tapes havedifferent lengths measured along a longitudinal axis of each of therespective tapes.
 11. The computer program product of claim 7, whereinselecting the first and second tapes is done pseudo-randomly.
 12. Thecomputer program product of claim 7, wherein the program instructionsare executable by the processor to cause the processor to: selecting athird tape that is different than the first and second tapes to write athird copy of the first portion of data to; and sending an instructionto write the third copy of the first portion of data to a thirdpartition on the third tape, wherein the third tape has at least a firstpartition, second partition and the third partition, wherein the firstpartition on the third tape is closer to a beginning of the respectivetape than the second and third partitions on the respective tape,wherein the second partition on the third tape is closer to thebeginning of the respective tape than the third partition on therespective tape.
 13. A computer program product comprising a computerreadable storage medium having program instructions embodied therewith,the program instructions executable by a processor to cause theprocessor to: receive, by the processor, a request to read a portion ofdata; determine, by the processor, whether the portion of data islocated in a first partition of a tape loaded in a tape drive; send, bythe processor, an instruction to read the portion of data from the firstpartition in response to determining that the portion of data is locatedin the first partition of the tape loaded in the tape drive; determine,by the processor, whether the portion of data is located in a secondpartition of the tape loaded in the tape drive in response todetermining that the portion of data is not located in the firstpartition of the tape loaded in the tape drive; and send, by theprocessor, an instruction to read the portion of data from the secondpartition in response to determining that the portion of data is locatedin the second partition of the tape loaded in the tape drive, whereinthe first partition is closer to a beginning of the tape than the secondpartition.
 14. The computer program product of claim 13, wherein theprogram instructions are executable by the processor to cause theprocessor to: determine, by the processor, whether the portion of datais located in a first partition of a tape in a tape library in responseto determining that the portion of data is not located in the secondpartition of the tape loaded in the tape drive; send, by the processor,an instruction to load a tape having the portion of data located in afirst partition thereof into the tape drive in response to determiningthat the portion of data is located in the first partition of the tapein the tape library; and send, by the processor, an instruction to readthe portion of data from the first partition of the tape loaded from thetape library.
 15. The computer program product of claim 14, wherein theprogram instructions are executable by the processor to cause theprocessor to: determine, by the processor, whether the portion of datais located in a second partition of a tape in the tape library inresponse to determining that the portion of data is not located in afirst partition of a tape in the tape library; send, by the processor,an instruction to load a tape having the portion of data located in asecond partition thereof into a tape drive in response to determiningthat the portion of data is located in the second partition of the tapein the tape library; and send, by the processor, an instruction to readthe portion of data from the second partition of the tape loaded fromthe tape library.
 16. The computer program product of claim 15, whereinthe program instructions are executable by the processor to cause theprocessor to: determine, by the processor, whether the portion of datais located in a third partition of a tape in the tape library inresponse to determining that the portion of data is not located in asecond partition of a tape in the tape library; send, by the processor,an instruction to load a tape having the portion of data located in athird partition thereof into a tape drive in response to determiningthat the portion of data is located in the third partition of the tapein the tape library; and send, by the processor, an instruction to readthe portion of data from the third partition of the tape loaded from thetape library.
 17. The computer program product of claim 16, wherein thetape having the portion of data in a third partition thereof also has afirst and second partition, wherein the first partition is closer to abeginning of the respective tape than the second and third partitions,wherein the second partition is closer to the beginning of therespective tape than the third partition on the respective tape.
 18. Thecomputer program product of claim 13, wherein the first partition on thetape loaded in the tape drive is closer to a beginning of the tape thanthe second partition.
 19. The computer program product of claim 13,wherein the first and second partitions on the tape loaded in the tapedrive each have an about equal length measured along a longitudinal axisof the tape.
 20. The computer program product of claim 13, wherein thefirst and second partitions on the tape loaded in the tape drive eachhave different lengths measured along a longitudinal axis of the tape.